Economic Space
What is the ZkAGI Economic Space?
The ZkAGI Economic Space is the layer where record-keeping and transactions are processed to ensure the $ZKAGI token economy fuels both agentic and user activity. It currently operates on Solana, with plans to expand to more chains and token-fiat rails for broader developer and user adoption.
- Record-keeping and transactions are processed to ensure the economy around $ZKAGI fuels agentic and user activity
- Currently operates on a blockchain like Solana
- Will be expanded to more chains and token-fiat rails to support developers and users from outside crypto
- The token operates in the economic space allowing agent-to-agent, agent-to-human, and human-to-agent payments for services on the network
How are compute payments handled in ZkAGI?
Compute payments in ZkAGI are resolved through the economic layer, where agents or developers pay for renting compute nodes running ZkAGI OS. API consumption payments and revenue splitting between end-user apps and the Zynapse API are also settled in this layer.
- Records for compute provisioning by nodes running ZkAGI OS and associated payments are resolved
- These payments are made by agents or developers renting the compute nodes
- API access: agents consume the Zynapse API by ZkAGI to keep performing actions
- End-user apps may add a markup on top of API consumption
- Payments for APIs and revenue splitting are resolved in the economic layer
How does ZkAGI handle wallet key security?
ZkAGI supports multiple wallet key storage models including local self-custodial storage, TEE-based autonomous custody, and secure hashed databases with 2FA. Each model offers different tradeoffs between automation convenience and user control over signing.
- Local storage on a user's machine or VPS — automations work in self-custodial wallets locally
- TEE-based custody — agent/autonomous custody and signing inside Trusted Execution Environments
- Secure hashed databases with dynamic salt — wallet keys locked with 2FA and password
- Agent recommends actions
- User must authenticate using both a password and 2FA before execution can happen